University of Minnesota Welcome Kit 2002

home *** CD-ROM | disk | FTP | other *** search

/ University of Minnesota Welcome Kit 2002 / PC Internet Tool.iso / pc / Extras / CLIENT32 / WIN95 / CLIENTV2 / ZSPE_1.EXE / README.TXT < prev next >

Wrap

Text File | 1998-05-13 | 24.8 KB | 535 lines

Z.E.N.works Starter Pack Release Notes Contents 1.0 Product Documentation 2.0 General Release Notes 3.0 Novell Client Software 4.0 NetWare Administrator 5.0 Workstation Registration 6.0 Trademarks 7.0 Disclaimer, Copyright, Export Notice ===================================================================== 1.0 Product Documentation To view Z.E.N.works overview documentation or Novell Client documentation directly from the CD, browse to the novdocs directory and double-click viewdoc.exe. The release notes for Novell clients (NT, WIN95, and DOS/WIN) are not included in this readme. They can be accessed on the CD when you choose to install client software. For complete Z.E.N.works Application Launcher readme information, view readnal.txt in products\zenworks\public\nls\<language> on the Z.E.N.works CD. For more information, see the following Web sites. http://www.novell.com/products/nds/zenworks (Sales Info., Papers) http://www.zenworks.com (Tips and Tricks) http://support.novell.com (NetWork Support Information) ===================================================================== 2.0 General Release Notes -Features Included in Z.E.N.works Starter Pack In conjunction with NDS and NetWare Administrator, Z.E.N.works uses NDS objects (such as Application, Workstation, and Policy Package objects) to provide the following features that help you manage workstations and applications. Distribute and maintain applications on the workstation Launch applications for users automatically on the workstation Import Workstation object information into NDS Dynamically distribute and update print drivers Centralize the location and administration of user profiles View and update client configurations without visiting the workstation Update workstation software automatically from your office Create Scheduled Actions for users (Available if using Desktop Management features, this automatically runs programs you especify for Windows 95** and Windows NT** clients) -Additional Features Available in Full Z.E.N.works Product With the full Z.E.N.works product (available from resellers), you can: Solve user software problems without visiting the workstation or NT server (using NDS-authenticated remote control). Provide end-users with a help request system. The Help Requester is an end user program that helps users provide pertinent information about themselves and their workstations to your Help Desk using e-mail or phone. This can mean faster problem resolution. Control the remote control feature and end-user help request system for workstations. You can set these once for a container or group or set them individually for users with special needs. Automatically place hardware inventory into NDS for tracking and troubleshooting. -Where files are installed The Z.E.N.works installation program on this CD installs files in sys\public on the NetWare server. The files on the CD are not compressed. -Installing Z.E.N.works from a server image If you copy Z.E.N.works from the CD onto a server, you will need to map root to the directory from where you run winsetup.exe. Otherwise, the installation program might not be able to locate certain help files. -Troubleshooting the import process If you attempt to import workstations by choosing Tools>Import Workstation, and you have an outdated version of COMCTL32.Dll, you won't be able to complete the import process. Either you won't see the dialog screen you need to complete the process, or you will get a GPF (general protection fault). A newer version of COMCTL32.Dll ships with the OSR2 release of Windows 95, as well as with recent versions of Microsoft's Internet Explorer. You can download the new file from: ftp://ftp.microsoft.com/softlib/mslfiles/COM32UPD.EXE or ftp://ftp.microsoft.com/softlib/mslfiles/40COMUPD.EXE -Removing Z.E.N.works Setup will exit if the uninstaller setup failed to initialize. If you check OK, you will get a blue screen that says SEVERE error--IRQL_NOT_LESS_OR_EQUAL address 80128709 base at 80100000 ntoskrnl.exe. To resolve this and uninstall Z.E.N.works, after logging in to the server, choose Control Panel>Add/Remove Program, select Z.E.N.works, and then choose the Add/Remove button. -Importing workstations on Windows NT When importing workstations using NetWare Administrator NT, the import process may fail to create a password for the new Workstation object. If you are importing from the NetWare Administrator NT Tools menu, you will receive an error message stating that the password could not be created. -Using on old COMCTL32.DLL with NetWare Administrator 95 Some Windows 95 administrative workstations may still be using a version of COMCTL32.Dll which does not include support for some components required by the Z.E.N.works NetWare Administrator snap-ins. To determine whether or not your Windows 95 administrative workstation has an outdated version of COMCTL32.DLL, do one of the following: *Check the Policies page in the Windows 95 User Package a. Run NetWare Administrator 32. b. Choose a Windows 95 User Package. c. Choose Details>Policies. If you don't see checkboxes in the left-hand column of the policies list, you have an old version of COMCTL32.Dll. *Attempt to import workstations a. Run NetWare Administrator 32. b. Highlight a container which has workstations to be imported. c. Choose Tools>Import Workstations. If nothing happens (no dialog box displays) or if you get a GPF, you probably have an old version of COMCTL32.Dll. A newer version of COMCTL32.Dll ships with the OSR2 release of Windows 95, as well as with recent versions of Microsoft's Internet Explorer. You can download the new file from: ftp://ftp.microsoft.com/softlib/mslfiles/COM32UPD.EXE or ftp://ftp.microsoft.com/softlib/mslfiles/40COMUPD.EXE -Using Dynamic Local User (DLU) with volatile user caching If you configure Dynamic Local User (DLU) in an NT User Policy Package to administer user access to NT Workstations, and if you use a credential set other than NetWare's credential set, the NT workstation user accounts created have a random unknown password and are created as volatile accounts. If volatile user caching is also enabled, the NT user accounts will persist on the workstation for the duration of the cache life. However, these accounts are inaccessible because they have an unknown password. If you use volatile user caching for users with non-NetWare credential sets, those NT User accounts will not be accessible unless the users log in to NDS concurrently and have the "Manage existing accounts" option set. -Using NDPS All administration for NDPS must be done using NetWare Administrator 95. NetWare Administrator 32 does not have NDPS support. And if you are installing NDPS with a Token Ring configuration you will need to get a patch from Microsoft. The patch fixes a known problem with large data transfer using WinSock over SPX. Fix ID number is Q171352. ===================================================================== 3.0 Novell Client Software -Accessing the user environment from Workstation Manager Schedule Action Items Z.E.N.works lets you create scheduled action items which are launched when users log in. You can schedule any service to be run. However, because the scheduled action process is launched from the Workstation Scheduler process, the environment of the current user logging in is not accessible by that service. Consequently, any process or application which is launched by Workstation Manager Scheduler cannot read or modify the current user's profile or environment. In most cases, services which are launched by the Workstation Manager Scheduler will not require this type of access. For example, Application Launcher Explorer will add items to the user's environment in order to integrate them into the Explorer desktop. However, if Application Launcher is configured as a scheduled action item to be launched at the time the user logs in, the Application Launcher will not be able to read the user's environment. This prevents the application from being able to integrate completely with the user's desktop. The current solution for this and other similar operations is to launch applications which require access to the user's environment from the user's login script. The next release of Z.E.N.works will solve this. -Using outdated Novell Client for Windows NT In NetWare Administrator, after you create a Policy Package object and modify a policy on the Policies page, you can use the Reset button on the Policies page to reset the highlighted policy to the default settings. After clicking Reset, if you receive a -601 error ("Object not found"), you are probably running an old version of the Novell Client for Windows NT. To resolve this, update your client to the one that ships with Z.E.N.works. Similarly, after you add a scheduled action to a policy package, if you receive an "Object not found" error, you are probably running an old version of the Novell Client for Windows NT. To resolve this, update your client to the one that ships with Z.E.N.works. -Primary network logon must be Novell NetWare Client Desktop preferences and user system policies are only processed when the primary network logon is Novell NetWare Client. -If you lose a network connection during installation During a client installation, if you lose a network connection and the screen pops up with a message to choose 'OK' or Enter, the end user should just wait for the client to automatically reconnect to the network. If the automatic client update terminates in the middle of an install, you may have to restart the installation. -Updating from a Z.E.N.works beta If you have installed a beta version of Z.E.N.works, and if you have older workstations in your NDS tree, then you should delete the workstations and run unreg32.exe in sys\public before installing the final Z.E.N.works. Unreg32.exe removes old Z.E.N.works registry entries and hidden files. -Running wm3x.exe (the DOS/Windows client) using Windows 3.x The Dos/Windows client, wm3x.exe, is intended to run at the end of startnet.bat (or before Windows 3.x loads). Running wm3x.exe after Windows is loaded (from a DOS box) could produce a GPF. -Persistent Caching Persistent name caching has been disabled. The maximum level that name caching can be set to is 1. -3.X Computer System Policy in NDS The ASCII text configuration files added to a Win 3.X Computer System Policy must not exceed 64K. If you store large text configuration files in NDS, they could cause heavy network traffic and slow down replica synchronization. If you wish to administer large text configuration files (greater than 32 KB), we recommend that you download them as binary files so that only the filenames are stored in NDS. ===================================================================== 4.0 NetWare Administrator -Using Z.E.N.works NetWare Administrator 32 Z.E.N.works supports NetWare Administrator 95 and NetWare Administrator NT. However, to take full advantage of the new features included in Z.E.N.works, you should use NetWare Administrator 32--the version of NetWare Administrator that ships with Z.E.N.works. -Enabling NetWare Administrator 32 for other Novell products Currently, NDS for NT, NRS and NetWare for SAA can be snapped-in to NetWare Administrator 32. To enable these products in NetWare Administrator 32, do the following: For NDS for NT v1.0, copy IWSAM.DLL ==> \PUBLIC\WIN32\SNAPINS IWSAM.HLP ==> \PUBLIC\WIN32\SNAPINS\NLS\ENGLISH IWSAMRES.DLL ==> \PUBLIC\WIN32\SNAPINS\NLS\ENGLISH For NRS v1.1, copy (Win95) NRSADM95.DLL ==> \PUBLIC\WIN32\SNAPINS\95ONLY NRSADMIN.HLP ==> \PUBLIC\WIN32\SNAPINS\95ONLY\NLS\ENGLISH NRSRES95.DLL ==> \PUBLIC\WIN32\SNAPINS\95ONLY\NLS\ENGLISH (WinNT) NRSADMNT.DLL ==> \PUBLIC\WIN32\SNAPINS\NTONLY NRSADMIN.HLP ==> \PUBLIC\WIN32\SNAPINS\NTONLY\NLS\ENGLISH NRSRESNT.DLL ==> \PUBLIC\WIN32\SNAPINS\NTONLY\NLS\ENGLISH For NetWare for SAA v3.0, copy (Win95) SAAN95.DLL ==> \PUBLIC\WIN32\SNAPINS\95ONLY SAAN95R.HLP ==> \PUBLIC\WIN32\SNAPINS\95ONLY\NLS\ENGLISH SAAN95R.DLL ==> \PUBLIC\WIN32\SNAPINS\95ONLY\NLS\ENGLISH (WinNT) SAANNT.DLL ==> \PUBLIC\WIN32\SNAPINS\NTONLY SAANNTR.HLP ==> \PUBLIC\WIN32\SNAPINS\NTONLY\NLS\ENGLISH SAANNTR.DLL ==> \PUBLIC\WIN32\SNAPINS\NTONLY\NLS\ENGLISH For more information on setting up NetWare Administrator snapins, go to http://support.novell.com and see TID #2937079. The following products currently do not support the snapin feature of NetWare Administrator 32: Fast Cache v2.0 GroupWise v5.2 NDPS v1.0 Border Manager v2.1 To use the snap-in feature of these products, please continue using either NetWare Administrator 95 or NetWare Administrator NT. -If you use NetWare Administrator 95 and NT Z.E.N.works requires that the dmpolicy.dll snap-in is the first Z.E.N.works snap-in loaded by NetWare Administrator 95 or NetWare Administrator NT (this does not apply if you are using NetWare Administrator 32). In some instances, NetWare Administrator 95 and NetWare Administrator NT do not read these dlls out of the registry in order. In these scenarios, the dmpolicy.dll snap-in will detect the problem and display a warning message recommending that you fix the problem. When dmpolicy.dll is not the first Z.E.N.works dll loaded, NetWare Administrator 95 and NetWare Administrator NT might have problems, like not being able to delete, move or rename Workstation objects, and certain Policy objects appearing in the Create Object dialog but not being able to be created there. The solution to this problem is to remove all Z.E.N.works snap-ins from the snap-in object registry for NetWare Administrator and then re-enter them so that they are loaded in the correct order. This process is simplified by a .reg file that is installed to the sys\public\win95 and sys\public\winnt directories on the server during Z.E.N.works installation which lists all registry keys needed for the Z.E.N.works snap-ins to work. Depending on your version of Z.E.N.works, this .reg file might be named zenstart.reg or zenfull.reg. To fix the problem: 1. Open the .reg file (either ZENSTART.REG or ZENFULL.REG) in Notepad or another ASCII text editor. 2. Open Regedit and manually delete the keys found in the .reg file. 3. Run "Regedit zenstart.reg" or "Regedit zenfull.reg" to reload the registry. -Problems using NetWare Administrator 95 and NT While NetWare Administrator 32 does not show Policy objects in the tree, if you run NetWare Administrator 95 or NT, you will see Policy objects are created along with the Policy Package objects. If you have several Policy Package objects, the number of Policy objects that get created in your tree can become cumbersome. -Authenticating to a new NDS tree using NWAdmin 95 and NT When running on the Z.E.N.works client, NetWare Administrator 95 and NT might be unable to launch the NetWare Login dialog when you try and browse to a tree to which you are not currently authenticated. However, you can task-switch to Windows Explorer, browse to the Network Neighborhood, and authenticate to the new tree without shutting down NWAdmnNT or NWAdmn95. When you return to NWAdmnNT or NWAdmn95, you should be able to browse to the new tree. This problem will not occur with NWAdmn32. -Policy objects may show up in NetWare Administrator 32 If you run NetWare Administrator 95 or NetWare Administrator NT, save settings, and run NetWare Administrator 32, you will see all the Policy objects in the browser window. To hide the policy objects in NWAdmin32, you can close all browser windows and open new browser windows, or you can remove the registry key for NWAdmin: HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator You can also hide Policy objects in NWAdmn95, NWAdmnNT, and NWAdmn32 if you use the View-Sort and Include dialog to remove individual policies from the current browser window and save your settings. -Running your snap-in DLLs using NetWare Administrator 32 NetWare Administrator 32 has support for old snap-in dlls (those compiled with snap-in95.lib or snap-inNT.lib) as well as new snap-in dlls (those compiled with snap-in32.lib). NetWare Administrator 32 includes shim dlls in the sys:public\win32 directory that support the old snap-ins. These have been included in the latest NetWare Administrator 32 build. They are: nwcore95.dll, nwcomn95.dll, nwvctl95.dll, nwcoreNT.dll, nwcomnNT.dll, and nwvctlNT.dll. They make calls into the corresponding NetWare Administrator 32 dlls (nwcore32.dll, nwcomn32.dll and nwvctl32.dll). To run a snap-in dll that has been installed with NetWare Administrator 95 or NT, copy the snap-in dll to the sys:public\win32\snap-ins directory and any supporting dlls to the sys:public\win32 directory. The snap-in directory is different if the snap-in only runs under NT (sys:public\win32\snap-ins\NTOnly) or 95 (sys:public\win32\snap-ins\95Only). You can get a list of the current snap-in dlls by looking at two registry keys under the NetWare Administrator key: HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator For NetWare Administrator 95: Snap-in Object DLLS WIN95 Snap-in View DLLS WIN95 For NetWare Administrator NT: Snap-in Object DLLS WINNT Snap-in View DLLS WINNT If the snap-in dll loads resource dlls or help files relative to NetWare Administrator (using NWAGetNLSFilePath), then copy the resource dlls and help files relative to the sys:public\win32 directory. If the snap-in dll loads resource dlls or help files relative to the snap-in dll, then copy the resource dlls and help files relative to the sys:public\win32\snap-ins directory. Novell recommends that you contact your vendor for a list of files and for the latest version of the snap-in dll. -Running numerous snap-ins with NetWare Administrator 32 If you have configured the registry for numerous snap-ins to load for NetWare Administrator 95 or NetWare Administrator NT, adding the Z.E.N.works snap-ins will cause the NetWare Administrator process to run out of "Thread Local Storage" handles. Windows 95 and Windows NT allocates 64 of these handles for the NetWare Administrator 95 or NT process. NWAdmin requires 17 handles. Each snap-in dll can require from zero to four or more of these "Thread Local Storage" handles. The ten Z.E.N.works snap-ins require four handles in all. If other snap-ins don't load or crash after adding the Z.E.N.works snap-ins, you have likely exceeded the 64 handle limit on your workstation. Novell snap-ins that consume multiple handles will be fixed in future releases. In the meantime, you can remove unnecessary snap-ins from the registry so that your necessary snap-ins will load. The NWAdmin snapin registry keys are: "HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator\Snapin Object DLLs WIN95" for NWAdmn95 and "HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare Administrator\Snapin Object DLLs WINNT" for NWAdmnNT. -Using Fastcache and BorderManager snap-ins Fastcache and BorderManager currently require NetWare Administrator NT in order to install the NT snap-ins for these products. NetWare Administrator NT does not ship with Z.E.N.works, so if you don't have this file and you wish to install one of these snap-ins, you will have to go to www.novell.com and download it. -Using NetWare Administrator 32 with NetWare 5 beta client Creating the Workstation Manager Client Configuration (WMCC) in NetWare Administrator 32 requires that the NetWare 5 beta Client for Windows 95 or Windows NT be installed on the workstation being used to create the policy. The snap-in depends on being able to access the GUI Login Active-X controls in order to properly configure the WMCC policy for login settings. -User profiles snap-in In the User profiles snap-in in NetWare Administrator 32, when you choose desktop preferences/display options/ and browse to a file name for either the screen saver or wallpaper, the snap-in will convert your local drive mappings to a UNC mapping. So when you type in a path, make sure the mapping you enter corresponds to the right UNC path on the local machine making the changes, not to the user's workstation. The program uses the current workstation mappings for the conversion. ==================================================================== 5.0 Workstation Registration -Workstation registration using Windows 95 You cannot manage workstations until a Workstation object is created and exists in your NDS tree. If you have problems registering workstations, do the following: 1. Run UNREG32.EXE from the server's PUBLIC directory. 2. Shutdown the workstation. 3. Using NWADMN32.EXE from the administrator's workstation, delete the Workstation Object in NDS 4. Restart the workstation. 5. From NWADMN32.EXE, import the workstation. 6. Right-click on the Workstation Manager icon in the taskbar tray and select Run Registration Agent Now. -Workstation registration using Windows 3.X If earlier versions of Workstation Manager have been installed (prior to Z.E.N.works), you must remove the workstation registration after installing Z.E.N.works and re-register the workstations. 1. Workstation Manager Installation Install Client32 and Workstation Manager for Windows 3.x. 2. Removing Workstation Registration From the Windows 3.x workstation, execute the unreg16.exe program from the server's PUBLIC directory. Now, use NetWare Administrator 32 to remove the Workstation object from NDS. 3. Workstation Registration From the workstation you wish to import, log on to the tree where you want to import the workstation. You can do this from the DOS prompt by typing LOGIN <treename>/<username>. After a successful log on, execute the registration agent WSREG16.EXE (found in the c:\novell\client32) directory. This will cause the workstation to appear in the list of importable workstations viewable from NetWare Administrator. 4. Import the Workstation From an administration workstation (the workstation that Z.E.N.works was installed from), run NetWare Administrator 32. Right-click the container of the user that logged on in step 1. Click the Workstation Registration button. Select the workstation(s) you wish to import, and click Import. This process will create a Workstation object in the tree. 5. Finalize Import Return to the DOS/WIN workstation and run the registration agent (WSREG16.EXE) a second time. -Automating workstation registration It is possible to automate the process of workstation registration by running WSREG16.EXE at the end of a container or user login script. If you choose to do this you should ensure that the login script will only be run on DOS/WIN workstations. -Using the scheduler to register workstations WSREG32.EXE cannot register and associate an NT Workstation if the logged on NT user does not have the rights to read and write to the registry. If users in your network don't have rights to modify the registry on their NT machines, use the scheduler to run WSREG32.EXE. ===================================================================== 6.0 Trademarks Novell Trademarks Novell and NetWare are registered trademarks of Novell, Inc. in the United States and other countries. IntranetWare, IntranetWare Client, NDS, and Z.E.N.works are trademarks of Novell, Inc. Third-Party Trademarks Windows and Windows NT are registered trademarks and Windows 95 is a trademark of Microsoft Corporation. ===================================================================== 7.0 Disclaimer, Copyright, Export Notice Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any Novell software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any Novell software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of recreating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell. Copyright (C)1998 Novell, Inc. All rights reserved. This product may not be exported outside the U.S. or Canada without prior authorization from the U.S. Department of Commerce.